The argument list doesn't provide the command used to generate the full workflow. So if I have something like:

o2-dpl-a | o2-dpl-b

Then the execution of each process gives me only this:

o2-dpl-b --id <some-device-from-b> --other-arguments

But I need this:

o2-dpl-a | o2-dpl-b | o2-dpl-b --id <some-device-from-b> --other-arguments

There is a solution with using intermediate files (cat dump.json), but I would like to avoid relying on generated files.

In principle, I could reconstruct the full command from DataProcessorInfos, which have exec name and args, but there is no unique identifier of a part of the merged workflow. So having duplicated executables in the same merged workflow would be quite troublesome:

o2-qc --config json:///a/b/c.json | o2-qc --config json:///d/e/f.json

Ok, thank you for your explanations.

I don't understand why o2-dataflow failed.

What was the error? It was transient in any case.

There was no error or failed test, but the check was marked as failed. Thanks for merging